Methods and apparatus for accessing localized applications

ABSTRACT

Methods of wireless communication and wireless transmit/receive units (WTRUs) are described. A WTRU includes a processor. The processor determines a location of the WTRU and whether an application is available to the WTRU based on the determined location of the WTRU. On a condition that the application is determined to be available to the WTRU based on the determined location of the WTRU, the processor initiates a registration to an application service hosting the application.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 61/533,047, which was filed on Sep. 9, 2011, and U.S.Provisional Patent Application No. 61/611,905, which was filed on Mar.16, 2012, the contents of which are hereby incorporated by referenceherein.

BACKGROUND

A location of a wireless transmit/receive unit (WTRU) may be determinedusing any number of different methods. One method commonly used for longterm evolution (LTE) is satellite assisted positioning, such as assistedglobal positioning system (GPS) (A-GPS). Satellite assisted positioningmay require GPS reception from four satellites and is generally suitablefor outdoor use. Another method commonly used for LTE is cell-basedpositioning. Cell-based positioning makes use of a server with knowledgeof the geographical location of the cell, timing alignment measurementsto determine a device's distance from the eNB's antenna, and neighborcell measurements to refine the accuracy. As with satellite assistedpositioning, cell-based positioning is generally suitable for outdooruse. Another method commonly used for LTE is observed time difference ofarrival (OTDOA) (also referred to as terrestrial GPS). OTDOA may requirereception from three different e-NodeBs (eNBs), and positioning usingOTDOA is based on the received timing difference from two cells relativeto the serving cell of the device. OTDOA is suitable for both indoor andoutdoor use. Typically, when a combination of A-GPS and one of the LTEfallback methods is used, the probability of accuracy within 150 m is95% but drops to 78% for 50 m.

For positioning in LTE, LTE typically provides a connection between theWTRU and a positioning server (LCS). The positioning server may requestthe WTRU to provide its location or, alternatively, may provide locationinformation to the WTRU, depending on the method used and the device'scapabilities. The positioning server may provide a list of potentialneighbor cells to search and assist in signal reception. The LTEpositioning protocol (LPP), as specified in 3GPP TS 36.355, may be used.The LPP includes a container mechanism for transport of additionalinformation. The LCS may be located anywhere in the network.

Other methods of determining the location of a WTRU may be used forother technologies. One other method is Wifi-based positioning, which isone of the positioning methods used by Google maps. Wifi-basedpositioning makes use of a server with knowledge of the geographicallocation of the Wifi transmitter and the service set identification(SSID). Neighbor SSIDs may be used to refine the accuracy. Wifi-basedpositioning is suitable for both indoor and outdoor use (although itsrange may be limited by the range of the Wifi technology in use).Another method is user provided positioning. For user-providedpositioning, a user may manually enter a location for use by anapplication. Another method is satellite-based positioning, such as pureGPS positioning at the application. Satellite-based positioning mayrequire GPS reception from four satellites and is generally suitable foroutdoor use. Another method is internet protocol (IP) address-basedpositioning. IP address-based positioning makes use of a server that hasknowledge of the geographical location of IP subnets. This method may belimited by network address translators (NATs), virtual private networks(VPNs) and other tunneling mechanisms. One other method is nearlocation-based services positioning, such as radio frequency (RF) ID(RFID), Bluetooth and infrared. Near location-based services positioningmay require use of multiple devices with in-built location parameters,GPS modules and/or a server with knowledge of the geographical locationof the devices.

SUMMARY

Methods of wireless communication and wireless transmit/receive units(WTRUs) are described. A WTRU includes a processor. The processordetermines a location of the WTRU and whether an application isavailable to the WTRU based on the determined location of the WTRU. On acondition that the application is determined to be available to the WTRUbased on the determined location of the WTRU, the processor initiatesaccess to an application service hosting the application.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,given by way of example in conjunction with the accompanying drawingswherein:

FIG. 1A is a system diagram of an example communications system in whichone or more disclosed embodiments may be implemented;

FIG. 1B is a system diagram of an example wireless transmit/receive unit(WTRU) that may be used within the communications system illustrated inFIG. 1A;

FIG. 1C is a system diagram of an example radio access network and anexample core network that may be used within the communications systemillustrated in FIG. 1A;

FIG. 2 is a diagram of a typical protocol stack for evolved packetsystem (EPS);

FIG. 3 is a flow diagram of a method of wireless communication;

FIG. 4 is a flow diagram of another method of wireless communication;and

FIG. 5 is a flow diagram of an example method of Wifi offload usinglocalized applications.

DETAILED DESCRIPTION

FIG. 1A is a diagram of an example communications system 100 in whichone or more disclosed embodiments may be implemented. The communicationssystem 100 may be a multiple access system that provides content, suchas voice, data, video, messaging, or broadcast to multiple wirelessusers. The communications system 100 may enable multiple wireless usersto access such content through the sharing of system resources,including wireless bandwidth. For example, the communications systems100 may employ one or more channel access methods, such as code divisionmultiple access (CDMA), time division multiple access (TDMA), frequencydivision multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrierFDMA (SC-FDMA), and the like.

As shown in FIG. 1A, the communications system 100 may include wirelesstransmit/receive units (WTRUs) 102 a, 102 b, 102 c, 102 d, a radioaccess network (RAN) 104, a core network 106, a public switchedtelephone network (PSTN) 108, the Internet 110, and other networks 112,though it will be appreciated that the disclosed embodiments contemplateany number of WTRUs, base stations, networks, and/or network elements.Each of the WTRUs 102 a, 102 b, 102 c, 102 d may be any type of deviceconfigured to operate and/or communicate in a wireless environment. Byway of example, the WTRUs 102 a, 102 b, 102 c, 102 d may be configuredto transmit and/or receive wireless signals and may include userequipment (UE), a mobile station, a fixed or mobile subscriber unit, apager, a cellular telephone, a personal digital assistant (PDA), asmartphone, a laptop, a netbook, a personal computer, a wireless sensor,consumer electronics, and the like.

The communications systems 100 may also include a base station 114 a anda base station 114 b. Each of the base stations 114 a, 114 b may be anytype of device configured to wirelessly interface with at least one ofthe WTRUs 102 a, 102 b, 102 c, 102 d to facilitate access to one or morecommunication networks, such as the core network 106, the Internet 110,and/or the networks 112. By way of example, the base stations 114 a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a HomeNode B, a Home eNode B, a site controller, an access point (AP), awireless router, and the like. While the base stations 114 a, 114 b areeach depicted as a single element, it will be appreciated that the basestations 114 a, 114 b may include any number of interconnected basestations and/or network elements.

The base station 114 a may be part of the RAN 104, which may alsoinclude other base stations and/or network elements (not shown), such asa base station controller (BSC), a radio network controller (RNC), orrelay nodes. The base station 114 a and/or the base station 114 b may beconfigured to transmit and/or receive wireless signals within aparticular geographic region, which may be referred to as a cell (notshown). The cell may further be divided into cell sectors. For example,the cell associated with the base station 114 a may be divided intothree sectors. Thus, in one embodiment, the base station 114 a mayinclude three transceivers, i.e., one for each sector of the cell. Inanother embodiment, the base station 114 a may employ multiple-inputmultiple output (MIMO) technology and, therefore, may utilize multipletransceivers for each sector of the cell.

The base stations 114 a, 114 b may communicate with one or more of theWTRUs 102 a, 102 b, 102 c, 102 d over an air interface 116, which may beany suitable wireless communication link (e.g., radio frequency (RF),microwave, infrared (IR), ultraviolet (UV), or visible light). The airinterface 116 may be established using any suitable radio accesstechnology (RAT).

More specifically, as noted above, the communications system 100 may bea multiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. Forexample, the base station 114 a in the RAN 104 and the WTRUs 102 a, 102b, 102 c may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA), whichmay establish the air interface 116 using wideband CDMA (WCDMA). WCDMAmay include communication protocols such as High-Speed Packet Access(HSPA) and/or Evolved HSPA (HSPA+). HSPA may include High-Speed DownlinkPacket Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

In another embodiment, the base station 114 a and the WTRUs 102 a, 102b, 102 c may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish the air interface116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A).

In other embodiments, the base station 114 a and the WTRUs 102 a, 102 b,102 c may implement radio technologies such as IEEE 802.16 (i.e.,Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000,CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), InterimStandard 95 (IS-95), Interim Standard 856 (IS-856), Global System forMobile communications (GSM), Enhanced Data rates for GSM Evolution(EDGE), GSM EDGE (GERAN), and the like.

The base station 114 b in FIG. 1A may be a wireless router, Home Node B,Home eNode B, or access point, for example, and may utilize any suitableRAT for facilitating wireless connectivity in a localized area, such asa place of business, a home, a vehicle, a campus, and the like. In oneembodiment, the base station 114 b and the WTRUs 102 c, 102 d mayimplement a radio technology such as IEEE 802.11 to establish a wirelesslocal area network (WLAN). In another embodiment, the base station 114 band the WTRUs 102 c, 102 d may implement a radio technology such as IEEE802.15 to establish a wireless personal area network (WPAN). In yetanother embodiment, the base station 114 b and the WTRUs 102 c, 102 dmay utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, orLTE-A) to establish a picocell or femtocell. As shown in FIG. 1A, thebase station 114 b may have a direct connection to the Internet 110.Thus, the base station 114 b may not be required to access the Internet110 via the core network 106.

The RAN 104 may be in communication with the core network 106, which maybe any type of network configured to provide voice, data, applications,and/or voice over internet protocol (VoIP) services to one or more ofthe WTRUs 102 a, 102 b, 102 c, 102 d. For example, the core network 106may provide call control, billing services, mobile location-basedservices, pre-paid calling, Internet connectivity, video distribution,and/or perform high-level security functions, such as userauthentication. Although not shown in FIG. 1A, it will be appreciatedthat the RAN 104 and/or the core network 106 may be in direct orindirect communication with other RANs that employ the same RAT as theRAN 104 or a different RAT. For example, in addition to being connectedto the RAN 104, which may be utilizing an E-UTRA radio technology, thecore network 106 may also be in communication with another RAN (notshown) employing a GSM radio technology.

The core network 106 may also serve as a gateway for the WTRUs 102 a,102 b, 102 c, 102 d to access the PSTN 108, the Internet 110, and/orother networks 112. The PSTN 108 may include circuit-switched telephonenetworks that provide plain old telephone service (POTS). The Internet110 may include a global system of interconnected computer networks anddevices that use common communication protocols, such as thetransmission control protocol (TCP), user datagram protocol (UDP) andthe internet protocol (IP) in the TCP/IP internet protocol suite. Thenetworks 112 may include wired or wireless communications networks ownedand/or operated by other service providers. For example, the networks112 may include another core network connected to one or more RANs,which may employ the same RAT as the RAN 104 or a different RAT.

Some or all of the WTRUs 102 a, 102 b, 102 c, 102 d in thecommunications system 100 may include multi-mode capabilities, i.e., theWTRUs 102 a, 102 b, 102 c, 102 d may include multiple transceivers forcommunicating with different wireless networks over different wirelesslinks. For example, the WTRU 102 c shown in FIG. 1A may be configured tocommunicate with the base station 114 a, which may employ acellular-based radio technology, and with the base station 114 b, whichmay employ an IEEE 802 radio technology.

FIG. 1B is a system diagram of an example WTRU 102. As shown in FIG. 1B,the WTRU 102 may include a processor 118, a transceiver 120, atransmit/receive element 122, a speaker/microphone 124, a keypad 126, adisplay/touchpad 128, non-removable memory 130, removable memory 132, apower source 134, a global positioning system (GPS) chipset 136, andother peripherals 138. It will be appreciated that the WTRU 102 mayinclude any sub-combination of the foregoing elements while remainingconsistent with an embodiment.

The processor 118 may be a general purpose processor, a special purposeprocessor, a conventional processor, a digital signal processor (DSP), aplurality of microprocessors, one or more microprocessors in associationwith a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Array (FPGAs)circuits, any other type of integrated circuit (IC), a state machine,and the like. The processor 118 may perform signal coding, dataprocessing, power control, input/output processing, and/or any otherfunctionality that enables the WTRU 102 to operate in a wirelessenvironment. The processor 118 may be coupled to the transceiver 120,which may be coupled to the transmit/receive element 122. While FIG. 1Bdepicts the processor 118 and the transceiver 120 as separatecomponents, it will be appreciated that the processor 118 and thetransceiver 120 may be integrated together in an electronic package orchip.

The transmit/receive element 122 may be configured to transmit signalsto, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, thetransmit/receive element 122 may be an antenna configured to transmitand/or receive RF signals. In another embodiment, the transmit/receiveelement 122 may be an emitter/detector configured to transmit and/orreceive IR, UV, or visible light signals, for example. In yet anotherembodiment, the transmit/receive element 122 may be configured totransmit and receive both RF and light signals. It will be appreciatedthat the transmit/receive element 122 may be configured to transmitand/or receive any combination of wireless signals.

In addition, although the transmit/receive element 122 is depicted inFIG. 1B as a single element, the WTRU 102 may include any number oftransmit/receive elements 122. More specifically, the WTRU 102 mayemploy MIMO technology. Thus, in one embodiment, the WTRU 102 mayinclude two or more transmit/receive elements 122 (e.g., multipleantennas) for transmitting and receiving wireless signals over the airinterface 116.

The transceiver 120 may be configured to modulate the signals that areto be transmitted by the transmit/receive element 122 and to demodulatethe signals that are received by the transmit/receive element 122. Asnoted above, the WTRU 102 may have multi-mode capabilities. Thus, thetransceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, forexample.

The processor 118 of the WTRU 102 may be coupled to, and may receiveuser input data from, the speaker/microphone 124, the keypad 126, and/orthe display/touchpad 128 (e.g., a liquid crystal display (LCD) displayunit or organic light-emitting diode (OLED) display unit). The processor118 may also output user data to the speaker/microphone 124, the keypad126, and/or the display/touchpad 128. In addition, the processor 118 mayaccess information from, and store data in, any type of suitable memory,such as the non-removable memory 130 and/or the removable memory 132.The non-removable memory 130 may include random-access memory (RAM),read-only memory (ROM), a hard disk, or any other type of memory storagedevice. The removable memory 132 may include a subscriber identitymodule (SIM) card, a memory stick, a secure digital (SD) memory card,and the like. In other embodiments, the processor 118 may accessinformation from, and store data in, memory that is not physicallylocated on the WTRU 102, such as on a server or a home computer (notshown).

The processor 118 may receive power from the power source 134, and maybe configured to distribute and/or control the power to the othercomponents in the WTRU 102. The power source 134 may be any suitabledevice for powering the WTRU 102. For example, the power source 134 mayinclude one or more dry cell batteries (e.g., nickel-cadmium (NiCd),nickel-zinc (NiZn), nickel metal hydride (NiMH), or lithium-ion(Li-ion)), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to the GPS chipset 136, which maybe configured to provide location information (e.g., longitude andlatitude) regarding the current location of the WTRU 102. In additionto, or in lieu of, the information from the GPS chipset 136, the WTRU102 may receive location information over the air interface 116 from abase station (e.g., base stations 114 a, 114 b) and/or determine itslocation based on the timing of the signals being received from two ormore nearby base stations. It will be appreciated that the WTRU 102 mayacquire location information by way of any suitablelocation-determination method while remaining consistent with anembodiment.

The processor 118 may further be coupled to other peripherals 138, whichmay include one or more software and/or hardware modules that provideadditional features, functionality and/or wired or wirelessconnectivity. For example, the peripherals 138 may include anaccelerometer, an e-compass, a satellite transceiver, a digital camera(for photographs or video), a universal serial bus (USB) port, avibration device, a television transceiver, a hands free headset, aBluetooth® module, a frequency modulated (FM) radio unit, a digitalmusic player, a media player, a video game player module, an Internetbrowser, and the like.

FIG. 1C is a system diagram of the RAN 104 and the core network 106according to an embodiment. As noted above, the RAN 104 may employ anE-UTRA radio technology to communicate with the WTRUs 102 a, 102 b, 102c over the air interface 116. The RAN 104 may also be in communicationwith the core network 106.

The RAN 104 may include eNode-Bs 140 a, 140 b, 140 c, though it will beappreciated that the RAN 104 may include any number of eNode-Bs whileremaining consistent with an embodiment. The eNode-Bs 140 a, 140 b, 140c may each include one or more transceivers for communicating with theWTRUs 102 a, 102 b, 102 c over the air interface 116. In one embodiment,the eNode-Bs 140 a, 140 b, 140 c may implement MIMO technology. Thus,the eNode-B 140 a, for example, may use multiple antennas to transmitwireless signals to, and receive wireless signals from, the WTRU 102 a.

Each of the eNode-Bs 140 a, 140 b, 140 c may be associated with aparticular cell (not shown) and may be configured to handle radioresource management decisions, handover decisions, scheduling of usersin the uplink and/or downlink, and the like. As shown in FIG. 1C, theeNode-Bs 140 a, 140 b, 140 c may communicate with one another over an X2interface.

The core network 106 shown in FIG. 1C may include a mobility managementgateway (MME) 142, a serving gateway 144, and a packet data network(PDN) gateway 146. While each of the foregoing elements are depicted aspart of the core network 106, it will be appreciated that any one ofthese elements may be owned and/or operated by an entity other than thecore network operator.

The MME 142 may be connected to each of the eNode-Bs 142 a, 142 b, 142 cin the RAN 104 via an S1 interface and may serve as a control node. Forexample, the MME 142 may be responsible for authenticating users of theWTRUs 102 a, 102 b, 102 c, bearer activation/deactivation, selecting aparticular serving gateway during an initial attach of the WTRUs 102 a,102 b, 102 c, and the like. The MME 142 may also provide a control planefunction for switching between the RAN 104 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

The serving gateway 144 may be connected to each of the eNode Bs 140 a,140 b, 140 c in the RAN 104 via the S1 interface. The serving gateway144 may generally route and forward user data packets to/from the WTRUs102 a, 102 b, 102 c. The serving gateway 144 may also perform otherfunctions, such as anchoring user planes during inter-eNode B handovers,triggering paging when downlink data is available for the WTRUs 102 a,102 b, 102 c, managing and storing contexts of the WTRUs 102 a, 102 b,102 c, and the like.

The serving gateway 144 may also be connected to the PDN gateway 146,which may provide the WTRUs 102 a, 102 b, 102 c with access topacket-switched networks, such as the Internet 110, to facilitatecommunications between the WTRUs 102 a, 102 b, 102 c and IP-enableddevices.

The core network 106 may facilitate communications with other networks.For example, the core network 106 may provide the WTRUs 102 a, 102 b,102 c with access to circuit-switched networks, such as the PSTN 108, tofacilitate communications between the WTRUs 102 a, 102 b, 102 c andtraditional land-line communications devices. For example, the corenetwork 106 may include, or may communicate with, an IP gateway (e.g.,an IP multimedia subsystem (IMS) server) that serves as an interfacebetween the core network 106 and the PSTN 108. In addition, the corenetwork 106 may provide the WTRUs 102 a, 102 b, 102 c with access to thenetworks 112, which may include other wired or wireless networks thatare owned and/or operated by other service providers.

3GPP LTE Releases 8, 9, 10 and 11 operating with a single serving cell(LTE R8+) supports up to 100 Mbps in the downlink (DL) and 50 Mbps inthe uplink (UL) for a 2×2 configuration. The LTE DL transmission schemeis based on an OFDMA air interface. For the purpose of flexibledeployment, LTE R8+ systems support scalable transmission bandwidths,for example, one of 1.4, 2.5, 5, 10, 15 or 20 MHz.

In LTE R8+(also applicable to LTE R10+ with carrier aggregation), eachradio frame (10 ms) may include 10 equally sized sub-frames of 1 ms.Each sub-frame may include 2 equally sized timeslots of 0.5 ms each.There may be either 7 or 6 OFDM symbols per timeslot. 7 symbols pertimeslot may be used with a normal cyclic prefix length, and 6 symbolsper timeslot may be used in an alternative system configuration with theextended cyclic prefix length. The sub-carrier spacing for the system ofLTE Releases 8 and 9 is 15 kHz. An alternative reduced sub-carrierspacing mode using 7.5 kHz is also possible.

A resource element (RE) may correspond to precisely 1 sub-carrier during1 OFDM symbol interval. 12 consecutive sub-carriers during a 0.5 mstimeslot may constitute 1 resource block (RB). Therefore, with 7 symbolsper timeslot, each RB may include 84 REs. A DL carrier may include ascalable number of RBs ranging from a minimum of 6 RBs up to a maximumof 110 RBs. This may correspond to an overall scalable transmissionbandwidth of roughly 1 MHz up to 20 MHz. However, a set of commontransmission bandwidths may be specified (e.g., 1.4, 3, 5, 10 or 20MHz).

The basic time-domain unit for dynamic scheduling is one sub-frameincluding two consecutive timeslots. This may be referred to as aresource-block pair. Certain sub-carriers on some OFDM symbols may beallocated to carry pilot signals in the time-frequency grid. A givennumber of sub-carriers at the edges of the transmission bandwidth maynot be transmitted in order to comply with spectral mask requirements.

For LTE, the DL physical channels may include, for example, a physicalcontrol format indicator channel (PCFICH), a physical hybrid automaticrepeat request (HARQ) indicator channel (PHICH), a physical data controlchannel (PDCCH), a physical multicast data channel (PMCH) and a physicaldata shared channel (PDSCH). On the PCFICH, the WTRU may receive controldata indicating the size of the control region of the DL CC. On thePHICH, the WTRU may receive control data indicating HARQacknowledgement/negative acknowledgement (HARQ A/N, HARQ ACK/NACK orHARQ-ACK) feedback for a previous UL transmission. On the PDCCH, theWTRU may receive DL control information (DCI) messages, which may beused to schedule DL and UL resources. On the PDSCH, the WTRU may receiveuser and/or control data. For example, a WTRU may transmit on a UL CC.

For LTE, the UL physical channels may include, for example, a physicalUL control channel (PUCCH) and a physical UL shared channel (PUSCH). Onthe PUSCH, the WTRU may transmit user and/or control data. On the PUCCH,and in some cases on the PUSCH, the WTRU may transmit UL controlinformation (such as CQI/PMI/RI or SR) and/or HARQ ACK/NACK feedback. Ona UL CC, the WTRU may also be allocated dedicated resources fortransmission of sounding and reference signals (SRS).

In an LTE system, the network (NW) may control physical radio resourcesusing a physical downlink control channel (PDCCH). Control messages maybe transmitted using specific formats (e.g., DCI formats). The WTRU maydetermine whether or not it needs to act on control signaling in a givensub-frame by monitoring the PDCCH for specific data control informationmessages (DCI formats) scrambled using a known radio network temporaryidentifier (RNTI) in specific locations, or search spaces, usingdifferent combinations of physical resources (e.g., control channelelements (CCEs)) based on aggregation levels (ALs), each correspondingto either 1, 2, 4, or 8 CCEs. A CCE may include 36 QPSK symbols or 72channel coded bits.

The PDCCH is conceptually separated into two distinct regions. The setof CCE locations in which a WTRU may find DCIs to act on is referred toas a search space (SS). The SS is conceptually split into a common SS(CSS) and a WTRU-specific SS (UESS). The CSS may be common to all WTRUsmonitoring a given PDCCH, while the UESS may differ from one WTRU toanother. Both SSs may overlap for a given WTRU in a given sub-frame asthis is a function of the randomization function, and this overlap maydiffer from one sub-frame to another.

The set of CCE locations that makes up the CSS, and its starting point,is a function of the cell identity and the sub-frame number. For LTER8/9, DCIs may only be sent with 4 CCEs (AL4) or 8 CCEs (AL8) in theCSS. For a sub-frame for which the WTRU monitors the PDCCH, the WTRU mayattempt to decode 2 DCI format sizes (e.g., formats 1A and 1C and alsoformat 3A used for power control) in up to 4 different sets of 4 CCESfor AL4 (i.e., 8 blind decoding) and up to 2 different sets of 8 CCEsfor AL8 (i.e., 4 blind decoding) for a total of at most 12 blinddecoding attempts in the CSS. The CSS may correspond to CCEs 0-15,implying four decoding candidates for AL4 (i.e., CCEs 0-3, 4-7, 8-11,12-15) and two decoding candidates for AL8 (i.e., CCEs 0-7, 8-15).

The set of CCE locations that makes up the WTRU SS, and its startingpoint, is a function of the WTRU identity and the sub-frame number. ForLTE R8+, DCIs may be sent with AL1, AL2, AL4 or AL8 in the WTRU SS. Fora sub-frame for which the WTRU monitors the PDCCH, the WTRU may attemptto decode 2 DCI formats in up to 6 different CCEs for AL1 (i.e., 12blind decoding), up to 6 different sets of 2 CCEs for AL2 (i.e., 12blind decoding), up to 2 different sets of 8 CCEs for AL8 (i.e., 4 blinddecoding) and up to 2 different sets of 8 CCEs for AL8 (i.e., 4 blinddecoding) for a total of at most 32 blind decoding attempts in the WTRUSS.

Which DCI formats the WTRU decodes depends on the configuredtransmission mode (e.g., whether or not spatial multiplexing is used).There are a number of different DCI formats (e.g., format 0 (UL grant),format 1 (non-MIMO), format 2 (DL MIMO) and format 3 (power control).The detailed format of the control messages are defined in 3GPP TS36.212. The version of each DCI format the WTRU may decode is governedat least in part by the configured transmission mode (e.g., modes 1-7for Release 8 and Release 9). A summary list with typical usage is asfollows: DCI format 0 (UL grant); DCI format 1 (DL assignment); DCIformat 1A (compact DL assignment/PDCCH order for random access); DCIformat 1B (DL assignment with precoding info); DCI format 1C (verycompact DL assignment); DCI format 1D (compact DL assignment withprecoding info+power offset info); DCI format 2 (DL assignment forspatial multiplexing); DCI format 2A; DCI format 3 (TPC for PUCCH/PDSCH,two bits); and DCI format 3A (TPC for PUCCH/PDSCH, single bit). Thedifferent DCI sizes resulting from different system bandwidthconfigurations is provided in Table 1 below.

TABLE 1 Bandwidth 6 15 25 50 75 100 Format 0 37 38 41 43 43 44 Format 1A37 38 41 43 43 44 Format 3/3A 37 38 41 43 43 44 Format 1C 24 26 28 29 3031 Format 1 35 39 43 47 49 55 Format 1B (2 tx ant) 38 41 43 44 45 46Format 1D (2 tx ant) 38 41 43 44 45 46 Format 2 (2 tx ant) 47 50 55 5961 67 Format 2A (2 tx ant) 44 47 52 57 58 64 Format 1B (4 tx ant) 41 4344 46 47 49 Format 1D (4 tx ant) 41 43 44 46 47 49 Format 2 (4 tx ant)50 53 58 62 64 70 Format 2A (4 tx ant) 46 49 54 58 61 66

In LTE R8+ systems, whether the control signaling received on PDCCHpertains to the UL CC or the DL CC is related to the format of the DCIdecoded by the WTRU, and the DCI formats may be used to control theWTRUs' communication on the UL CC and the DL CC of the cell to which theWTRU is connected.

A WTRU may request radio resources for a UL transmission by sending ascheduling request (SR) to the eNB. The SR may be transmitted either ondedicated resources (D-SR) on the PUCCH if configured or using therandom access procedure (RACH) otherwise.

SRBs are radio bearers used only for the transmission of RRC and networkaccess server (NAS) messages. SRB0 is used for RRC messages using thecommon control channel (CCCH) logical channel, SRB1 is for RRC messages(with a piggybacked NAS message in an embodiment) and for NAS messagesprior to establishment of SRB2 using the dedicated control channel(DCCH) logical channel, while SRB2 is for NAS messages and is configuredafter activation of security. Once security is activated, RRC messageson SRB1 and SRB2 are integrity protected and ciphered. DRBs are radiobearers mainly used for the transmission of user plane data (e.g., IPpackets).

RRC handles the control plane signaling and the exchange of layer 3messages between the eNB and the WTRU. E-UTRA defines two RRC states:RRC_CONNECTED and RRC_IDLE. The WTRU is in RRC_CONNECTED when an RRCconnection has been established; otherwise, the WTRU is in RRC_IDLE. Inthe RRC_IDLE state, the WTRU at least monitors the paging channel todetect incoming calls, change of system information, and, in anembodiment, also early terrestrial warning system (ETWS)/commercialmobile alert system (CMAS) notifications and performs neighboring cellmeasurements and cell (re-)selection and system information acquisition.In the RRC_CONNECTED state, the WTRU may transmit/receive on unicastchannels and at least monitor the paging channel and/or systeminformation block type 1 to detect incoming calls, change of systeminformation, and, in an embodiment, ETWS/CMAS notifications. The WTRUmay also be configured with one or more secondary cells in addition tothe primary cell. The RRC protocol is specified in 3GPP TS 36.331 andincludes a definition of states, state transitions, messages (e.g.,protocol data units (PDUs)) and related procedures.

The NAS layer handles mobility-related functions between the WTRU andthe core network, such as the attach procedure and the tracking areaupdate (TAU) as well as the authentication and security functions. TheNAS layer also establishes and maintains IP connectivity between theWTRU and the core network.

The NAS protocol is logically transmitted on the control plane,typically over signalling radio bearers (SRBs) between the WTRU and thecore network. In the Evolved Packet System (EPS), the endpoint in the CNis the mobility management entity (MME).

FIG. 2 is a diagram 200 of a typical protocol stack for EPS. Theprotocol stack includes a protocol stack NAS 202, eNBs 204 and 206 andan MME 208. The NAS includes an RRC layer 210, a PDCP layer 212, an RLClayer 214, a medium access control (MAC) layer 216 and physical (PHY)layer 218. The eNB 204 includes an RRC layer 220, a PDCP layer 222, anRLC layer 224, a MAC layer 226, a PHY layer 228, an S1 AP layer 230, anX2 AP layer 232, an SCTP layer 234, an IP layer 236 and an L1/L2 layer238. The eNB 206 includes an X2 AP layer 240, an SCTP layer 242, an IPlayer 244 and an L1/L2 layer 246. The MME 208 includes an NAS protocolstack, including an 51 AP layer 248, an SCTP layer 250, an IP layer 252and an L1/L2 layer 254. The MME 208 also includes a GTP-C layer 256, aUDP layer 258, an IP layer 260 and an L1/L2 layer 262.

In the embodiments described below, the WTRU and/or the network (e.g.,the eNB) may be equipped with the ability to determine at least someposition-related parameters according to, for example, at least one ofsatellite assisted positioning, cell-based positioning, OTDOA,Wifi-based positioning, user provided positioning, satellite-basedpositioning, IP address-based positioning, near location-basedpositioning, or any other positioning method. Accordingly, positioninginformation for a concerned device may be available and/or may beobtained by some means.

Embodiments described herein relate to how a WTRU may initiate andestablish a communication with one or more devices to access anapplication, the availability of which may be location-dependent. Theapplication may be, for example, a peer-to-peer or a client-serverapplication. This type of application may not require use of batteryconsuming positioning services, may provide the possibility ofperforming device to device communications bypassing the control networkfor at least the user data plane, and may enable push services based onWTRU mobility. Thus, it may be desirable to provide such services withreduced signaling, latency and WTRU power consumption compared to usingthe combination of a GPS device and the mobile network as the data pipefor the connection.

The range of device-to-device communications deployment may includeanything from methods applicable in uncoordinated mesh networks in, forexample, an unlicensed spectrum (e.g., using carrier sensing approaches)to methods applicable in network-managed communications in, for example,a licensed spectrum (e.g., a scheduler may allocate radio resources todevice-to-device communications in a given geographical area).Similarly, applications that use device-to-device communications mayinclude anything from peer-to-peer applications to client-serverapplications for services including, for example, social networking,marketing services and public safety applications. Examples of socialnetworking applications may include Facebook, Linked-In, Google+hangouts, get in touch applications such as online dating services,Latitude services, messaging and chat sessions, collaborative gaming orcollaborative virtual working environments (including, for example, avirtual LAN). Examples of marketing services applications may includepromotional offers (e.g., FourSquare), automated services (e.g., airportcheck-in), localized tourist information, contextual and/or in-storeconsumer information, on-demand contextual/location-based marketing andpublicity, and mobile payments.

In addition to offering LTE services, for example, operators may alsooffer support for Wifi services (e.g., in hot spot areas) using, forexample, one or more Wifi technologies such as 802.11b/g/n in the 2.4GHz frequency band, 802.11y in the 3.6 GHz frequency band and/or802.11a/h/j/n in the 5 GHz frequency band. Operators may deploy theirWifi services as a Wifi offload application or as Wifi aggregation.

Operators may offer services through LTE femto-cells, Home NBs (forHSPA) and/or Home eNode Bs (for LTE) as an offload application. In anembodiment, a Wifi offload may be characterized by one or more securityparameters such as: the type of security protocol (e.g., one of a wiredequivalent privacy (WPA), Wifi protected access (WPA) or WPA II (WPA2));the type of encryption algorithm (e.g., one of a temporal key integrityprotocol (TKIP), or a pre-share key mode (PSK)) and; the security key(e.g., a string of hexadecimal digits or a bitstring, which may, in anembodiment, correspond to information (e.g., a passphrase) from which aWifi device further derives the encryption key using a known keyderivation function). Wifi services may also be implemented using IEEE802.16 or IEEE 802.20.

A Wifi local area network (WLAN) or Wifi may refer to any type of IEEE802.11, 802.16 or 802.20 access. A WLAN WTRU may be a WTRU that supportsand implements one or more 3GPP RAT and one or more Wifi technology. AWLAN AN may be a network node that implements Wifi access and thatprovides IP network connectivity. A WLAN AP may be an access point thatimplements Wifi access to a WLAN AN. In an embodiment, a WLAN AP mayinclude a network node that supports and implements one or more 3GPP RAT(e.g., HSPA NB, LTE eNB) and one or more Wifi technology. Mobility withWifi technology may be limited to pedestrian mobility, when the WLANWTRU moves from one WLAN AP to another WLAN AP of the same WLAN AN.

A WLAN WTRU may first establish an association with a WLAN AP beforeexchanging data with a WLAN AN. The WLAN WTRU may first discover theavailable WLAN AN, then select one and perform authentication (ifneeded), and finally associate itself with the access point. The WLANWTRU may be synchronized with the WLAN AN and may start sending dataframes.

The IEEE 802.11 specification defines two different methods to discoveravailable access points, namely passive scanning and active scanning.Using those methods, the WLAN WTRU may determine a list of availableWLAN ANs, and user input may be required unless it is configured toautomatically reconnect to a known WLAN AN.

An access point periodically broadcasts a beacon signal that may bereceived by a WLAN WTRU to determine a number of parameters of thecorresponding WLAN AN (e.g., SSID or supported rates) as well asreceived signal strength. When using passive scanning, the WLAN WTRU maycollect information without transmitting a request (e.g., based onsignals that it can receive).

When using active scanning, the WLAN WTRU transmits a broadcast framefor which any access point in range may respond with a probe response.Active scanning is optional, and may incur additional overhead on thenetwork for the transmission of probe signals on the shared medium.

To improve the discovery and selection of WLAN ANs, IEEE 802.11uspecifies network discovery and selection methods. The WLAN WTRU mayreceive additional information through advertisement services prior toperforming association with a WLAN AN using a transport mechanism termedGAS. GAS is a transport protocol for different advertisement protocols,and GAS transmissions may be received by WLAN WTRUs in an associated orunassociated state. The WLAN WTRU may determine that the WLAN ANsupports IEEE 801.11u using the interworking element. The WLAN WTRU maypost a query to a discovered SSID (e.g., using either passive or activescanning). The WLAN may then receive from a WLAN AN a responseindicating operator-related parameters.

Discovery-related information may include parameters such as accessnetwork type [range 0-15] (e.g., private network, private network withguest access, chargeable public network, or free public network),roaming information, and venue information. Selection-relatedinformation may result from a query from the WLAN WTRU and may includeparameters such as domain name, credential type and EAP methods.

Based on stored credentials and operator policies, and, in anembodiment, also based on user interactions, the WLAN WTRU may determinewhat WLAN AN to associate with. Roaming agreements between differentIEEE 802.11 networks may be implemented. A protocol called SSPN supportscommunication to the access point, such that user credentials and userpolicies may be communicated to the WLAN AN.

3GPP has worked on a number of different solutions to support access toWLAN networks as means to perform interworking between WLAN accessnetworks with the possibility to offload user traffic. For example, 3GPPTS 23.234 describes methods for a WLAN WTRU to achieve internetconnectivity and access 3GPP PS services using authentication andauthorization via the 3GPP system. The described methods require theestablishment of a tunnel between the WLAN WTRU and the packet datagateway (PDG) in the 3GPP CN. 3GPP TS 23.234 also describes methods fora WLAN WTRU to receive IP-related configuration parameters from a 3GPPCN node, such as remote IP address, DHCP server and DNS server for theHPLMN. 3GPP TS 23.234 also describes WLAN direct IP access where theWLAN WTRU only has a local IP address (e.g., a WLAN AN identity), andWLAN 3GPP IP access where the WLAN WTRU has both a local IP address (theouter IP address of the tunnel) and a remote IP address (the inner IPaddress of the tunnel), which may be assigned by the WLAN AN or the PLMNwithin the WLAN AN IP address space.

For another example, 3GPP TS 23.402 describes architecture enhancementsfor non-3GPP accesses, a reference architecture for integrating WLAN asan un-trusted access to the 3GPP evolved packet core (EPC), and methodsto connect WLAN to the evolved packet data gateway (ePDG) that supportsPMIPv6 and GTP mobility.

For another example, 3GPP TS 23.261 describes IP flow mobility andseamless WLAN offload. For another example, 3GPP TS 23.303 describesmethods to perform IP mobility between a 3GPP access and a WLAN accessbased on DSMIPv6.

In addition, some proprietary efforts have been discussed, such as, forexample, Qualcomm's WTRU-centric connectivity engine (CnE), whichdiscusses a framework for a 3G/LTE Wifi offload framework. The aim ofthe framework is to allow the routing of specific IP services (e.g.,HTTP, video streaming, VoIP) over either a 3G/LTE radio interface orover a Wifi interface. The proposed framework consists of threecomponents: a mechanism to provide operator policy, possiblydynamically, algorithms in the device to detect characteristics ofunplanned Wifi networks (the focus is for the WTRU to autonomouslydetermine what is the best possible use of the available networks) and amechanism to allow transparent handovers between 3G/LTE and Wifi.

In particular, the Qualcomm implementation relies on the above-describedstandard 3GPP technology and describes WTRU-centric, WTRU-autonomous andmostly implementation-related techniques to perform measurements andWTRU-initiated handovers. In other words, the methods described rely onthe establishment of a connection to the 3GPP CN and do not includemethods for the network to control how the WTRU accesses the 3GPP andthe WLAN AN beyond those existing for CN-based seamless IP mobility.

In general, all of the above solutions are based on establishingconnectivity between the WLAN access node (WLAN AN) and the 3GPP corenetwork (3GPP CN) and require authentication, authorization andestablishment of a tunnel between the WLAN WTRU and the 3GPP CN. Inother words, the principle applied is that the WLAN access is a separateand independent access technology from other 3GPP accesses (e.g., LTE,WCDMA/HSPA) and uses the facilities of the 3GPP CN to provide means foran operator to offer WLAN services including differentiated QoS andcharging for the concerned data transfers. The switching of the trafficmay be based on operators' policies and may be performed in the 3GPP CN.This approach may have some drawbacks in terms of deployment costs, suchas deployment of a stand-alone WLAN AN and impact to existing CN nodes.

Embodiments described herein generally refer to the two following typesof Wifi offload services: cellular-assisted with redirection Wifioffload and cellular-controlled Wifi offload. For cellular-assisted withredirection Wifi offload, the WLAN WTRU may establish an associationwith a WLAN AP following signaling received on an RRC connectionestablished with a cellular system (e.g., a macro cell such as either anHSPA WTRU or an LTE WTRU). The signaling may be similar to an inter-RAThandover from a 3GPP access to a Wifi access. For cellular-controlledWifi offload, the WLAN WTRU may establish an association with a WLAN APwhile it maintains its RRC connection to, for example, a macro cell(e.g., either as an HSPA WTRU or an LTE WTRU). In other words, the WLANWTRU may concurrently operate on the Wifi AN and on an HSPA or LTE radioaccess.

3GPP has also discussed the possibility of supporting interworkingbetween WLAN AN and 3GPP accesses, with focus on solutions that wouldallow a tighter integration between the two accesses as well as avoidingthe need for a duplicate 3GPP CN functionality. Discussions haveincluded the possibility of performing some form of carrier aggregationwhile minimizing changes to the WLAN AN and the WLAN air interface. Theenvisioned deployment scenario includes small 3GPP cells (e.g., pico,femto, relays) integrated with Wifi radio or remote radio elements(RRHs) with Wifi radio.

There have also been discussions in 3GPP summarizing the differentcurrently available CN-based alternatives as well as the above mentioneddeployment scenario for consideration. The discussion focused on someform of aggregation between 3GPP LTE and Wifi, although extending thestudy to 3GPP HSPA should not be precluded despite the drawback ofpossibly requiring changes to the 3GPP RNC.

While embodiments are described herein with respect to Third GenerationPartnership Project (3GPP) LTE technology, it may be equally applicableto other wireless technologies.

In embodiments described herein, client-server communications mayinclude, for example, distributed applications that may involve aplurality of devices and which may partition tasks and resources suchthat a peer is either a supplier (sender) or a consumer (receiver) ofthe resources (e.g., application data). For example, this type ofcommunication may involve a server that provides a service above the IPlayer (e.g., an application server). For example, this type ofcommunication may involve one or more network elements that provideservices to a client such as allocation of radio resources (e.g. a femtocell network element, a base station (e.g., a Home Node B or a HomeeNB), a WTRU that can provide direct WTRU to WTRU communication or anaccess point such as a Wifi access point).

In embodiments described herein, peering may include, for example,distributed applications that may involve a plurality of devices whichmay form a group and/or a peer-to-peer network. For example, this typeof communication may involve one or more devices that exchange data fora given distributed IP application. For example, this type ofcommunication may involve one or more network elements that communicatein a coordinated manner using radio resources such as a Wifi network.

From a physical layer perspective, peering may be realized, for example,using direct device-to-device transmissions, transmissions scheduled bya controlling network node using dedicated resource allocation, using ashared medium which access may be based on carrier sensing and/orinvolving broadcast/multicast transmissions within a coverage area. Froma transport layer perspective (e.g., IP), peering may include unicasttransmissions between a plurality of peers and/or multicasttransmissions. For unicast transmissions, multiple copies of the sameapplication data may be transmitted either by the originating device orby an application server towards multiple connected peers each using adifferent IP flow. For multicast transmissions, a single copy of theapplication data may be transmitted towards the network as a single IPflow, which data may be replicated by one or more network node towardseach peer subscribed to the multicast flow. From an application layerperspective (e.g., a group chat application), peering may include anyapplication that involves a plurality of devices where peers are bothsuppliers (senders) and consumers (receivers) of resources (e.g.,application data). Thus, a peering communication may refer to anycombinations of the above. For example, it may include a peer-to-peerapplication transported (e.g., a multiuser videoconference or a chatapplication) over a unicast protocol (e.g. RTP/UDP, or TCP/IP) usingdedicated radio resources (e.g., PDCCH scheduled by PDCCH) over a radiolink (e.g., LTE).

In embodiments described herein, a pull service may include, forexample, a service by which a client would typically initiate acommunication session with a server or another peer, which server/peermay await incoming requests. Further, in embodiments described herein, apush service may include, for example, a service by which a server mayinitiate the transfer of application data (e.g., including initiating acommunication session or using an existing session) with a client oranother peer, which client/peer may accept incoming application data.

In the embodiments described herein, a localized application may includeany form of client-server communication or peering communication (e.g.,including pull and push applications) between one or more mobile devicesand zero (e.g., direct device-to-device communications) or more (e.g.,for network-controlled communications over radio resources) networkentities (e.g., an eNB, MME, localized application information server(LAIS)). In an embodiment, a localized application may additionallyrefer to a session of the application. For example, a session may beshared by a plurality of WTRUs that belong to the same group (e.g.,friends, circles, community groups, or professional groups). Groupingand/or session information may be based on subscriber profileinformation, positioning information, or service subscription, or may beselected upon access to the LAIS (e.g., user-selected uponregistration). In addition, a localized application may also refer toconnectivity to a network element, such as a cell from a same or adifferent type of RAT (e.g., LTE, HSPA or Wifi), for example foroffloading traffic from one RAT to another.

FIG. 3 is a flow diagram 300 of a method of wireless communication. Inthe example illustrated in FIG. 3, a WTRU determines its location 302.The WTRU may determine whether an application is available to the WTRU,for example, based on the determined location of the WTRU (304). TheWTRU may initiate access to an application service hosting theapplication if the application is determined to be available to the WTRU(306). In an embodiment, the WTRU may initiate access the applicationservice by initiating registration to the application service.

FIG. 4 is a flow diagram 400 of another method of wirelesscommunication. In the example illustrated in FIG. 4, a WTRU receives anindication from an application service that a given application hostedby the application service is available to the WTRU (402). In anembodiment, the indication may be an indication that the WTRU is withina location area of the given application hosted by the applicationservice. The WTRU may initiate access to the application service hostingthe given application in response to receiving the indication (404). Inan embodiment, the WTRU may initiate access to the application serviceby initiating registration to the application service.

Whether an application is available to the WTRU (e.g., 304 or 402) maybe determined based on, for example, localized applications information(LAI). LAI may be structured, for example, as a list of one or moreelements, and each element in the list may correspond to informationrelating to a particular application. Each element in an LAI may includeas least one of an application identity, an application type, a locationarea for a given application, a coverage area for a given application,an availability of a given application, access credentials required fora given application, communication parameters for a given applicationand application triggers.

An application identity may be used to identify a specific applicationfor different transactions (e.g., registration, de-registration, orapplication setup). An application type may be used to determine asubset of applications for different transactions (e.g., registration).

With respect to a location area for a given application, theavailability and/or accessibility of an application may be a function ofa positioning criterion. On a condition that the criterion is met, anentity (e.g., a WTRU or a network node such as LAS) may determine that aWTRU may perform further procedures related to the application. Forexample, the WTRU may register to the concerned application (e.g.,availability) and/or initiate communication for the concernedapplication (e.g., accessibility) when the criterion is met. Forexample, an application may be available within a specific geographicalarea. As another example, the criterion may be that the WTRU's positionis within a certain area. Examples of such areas may include ageographical position with a given error margin, a sector of a cell, acell, reception of signals from a given eNB, reception ofdiscovery-related signals from a second WTRU, a tracking area, or a cellserved by a given MME. For example, a WTRU in idle mode may perform cell(re-)selection and camp on a selected cell. The WTRU may then determinethat a localized application of interest is available in the selectedcell and determine that it may access the application only based on theavailability of the application in the cell. The WTRU may then initiatecommunication for the application.

With respect to coverage area for a given application, if the coveragearea is different than the location area for the given application(e.g., a coverage area is indicated and is smaller than the locationarea), the accessibility of an application may further be a function ofa positioning criterion. On a condition that the criterion is met, anentity (e.g., a WTRU or a network node such as LAS) may determine that aWTRU may perform further procedures related to the application. Forexample, if the WTRU is already registered to the application or ifregistration is not necessary for the concerned application, the WTRUmay initiate communication for the concerned application (e.g.,accessibility) when the criterion is met. For example, an applicationmay be accessible within a specific geographical area (e.g., a cell),which area may be a subset of the location area (e.g., a tracking areathat includes a plurality of cells). As another example, the criterionmay be that the WTRU's position is within a certain area. Examples ofsuch areas may include a geographical position with a given errormargin, a sector of a cell, a cell, reception of signals from a giveneNB, reception of discovery-related signals from a second WTRU, atracking area, or a cell served by a given MME. For example, a WTRU inidle mode may perform cell (re-)selection and camp on a selected cell.The WTRU may then determine that a localized application of interest isavailable in the selected cell. The WTRU may further initiate aprocedure to determine/obtain its location (e.g., using a positioningmethod) and further determine that it may access the application basedon the WTRU's position being within the coverage area of the concernedapplication (expressed as a geographical area in an embodiment). TheWTRU may then initiate communication for the application. The coveragearea for an application may be equal to its location area.

With respect to availability of a given application, the availability ofa given application may be a function of whether or not at least onepeer and/or server may communicate. For example, for client-serverapplications, a service may be available if a server is registeredand/or may receive new requests from clients. For another example, forpeering applications, the application may be available if the number ofdevices interested in (and/or registered for) the service, excluding theWTRU, is greater than a specific threshold for the service (e.g.,greater than zero). For another example, for network offloadingapplications, the application may be available if the access credentialsof the WTRU indicate that the offload cell and/or network may beaccessed by the WTRU. For example, for a Wifi offload application, thismay be based on subscriber type and/or an identity of the Wifi network(e.g., basic SSID and/or a MAC identity) and/or one or more securityparameters. For a Home eNB or similar node, this may be based a closedsubscriber group (CSG) identification (CGI), a physical cellidentification (PCI) and/or a CSG list.

With respect to access credentials required for a given application, theapplication may require a transaction to determine whether or not a WTRUthat initiates communication with a service has sufficient credentials.For example, this may include a subscriber's identification, one or moresecurity keys for authentication and/or encryption, one or more securityalgorithms for authentication and/or encryption, and groupidentification.

Communication parameters for a given application may include at leastone of IP addresses for the application, transport protocol type for agiven application, port numbers for a given application, SIP/URL,MBMS-related information or security-related parameters (e.g.,application-level encryption parameters). For client-serverapplications, for example, IP addresses for the application may includethe IP address of a server (e.g., corresponding to another mobiledevice). For peering applications, for example, IP addresses for theapplication may include the IP address of a peering application server,the IP address of one or more other peers (e.g., corresponding to otherWTRUs) or a multicast IP address.

A transport protocol type for a given application may be, for example,TCP (e.g., for client-server type of applications) or UDP (e.g., forpeering applications). Port numbers for a given application may include,for example, a TCP port number (e.g., for client-server type ofcommunication) or a UDP port number (e.g., for peering applications).

Any of the IP addresses for the application, transport protocol type fora given application, and port numbers for a given application may beincluded in an SIP message and/or a URL.

For an application that may be transmitted using MBMS channels,MBMS-related information may include parameters that may allow the WTRUto determine, for example, what MBSFN area (e.g., the MBMS cell groupidentity) and/or what MBMS control channel (MCCH) may be used to accessthe DL broadcast for a given application. In an embodiment, this mayalso include an identity of the MBMS service that corresponds to theconcerned application.

With respect to application triggers, application triggers may includeone or more condition that, when true, may trigger the WTRU to registerto an application and/or a session, for example, to access anapplication and/or a session or to terminate its registration to anapplication. For example, this may include positioning information forproximity detection such that a WTRU may autonomously register and/orinitiate access to the application when detecting that it is within acertain distance of the indicated position.

A WTRU may receive, transmit and/or store LAI. In an embodiment, a WTRUmay obtain LAI from another WTRU. In another embodiment, a WTRU mayobtain LAI from a network entity (e.g., an LAI server (LAIS)). Otherentities may access at least part of the LAI. For example, a networkentity may store and exchange the above information with a WTRU.

To determine whether a WTRU is in an area that supports localizedapplications (e.g., whether a serving cell supports localizedapplications), the WTRU may maintain one or more parameters related tosupport of localized applications within a given cell. Examples of suchparameters may include indication of support for localized applications,scheduling information, and LAI for one or more applications availablein the concerned cell. Alternatively, the WTRU may receive signalingthat includes at least some of the above parameters via at least one ofbroadcasted information, dedicated signaling and higher layer signaling.

An indication of support for localized applications may include, forexample, an indicator bit and/or the presence of an information elementin received signaling that provides, for example, further cell-specificparameters used to access localized applications in the concerned cell.For example, a WTRU may detect the presence of a system informationblock (SIB) for localized applications in the broadcast systeminformation for the cell and determine that localized applications aresupported for the concerned cell. In an embodiment, this may include anindication of whether or not registration of services and/or initiationof services not currently available for the concerned cell is supported(e.g., the list of advertised applications may be semi-static and readonly for WTRUs).

Scheduling information may include, for example, a specific RNTI (e.g.,an LA-RNTI) for scheduling further cell-specific parameters used toaccess localized applications in the concerned cell. In an embodiment, aset of one or more subframes and/or transmission timing may be used forthe scheduling of the further cell-specific parameters. For example, theWTRU may receive, on an SIB applicable to localized applications, anRNTI that the WTRU may use to decode further parameters (e.g., a list ofapplications available in the concerned cell and applicable parameters,if any) scheduled on, for example, the PDSCH.

LAI for one or more applications available in the concerned cell mayinclude a list of available services and/or service types (e.g., serviceadvertisement). This may include, for example, a list of one or moreapplications available in the concerned cell and applicable parameters.For example, the WTRU may receive this information on an SIB applicableto localized applications or on a separate transmission (eitherbroadcast or dedicated) on the PDSCH. The WTRU may use the LAI todetermine whether or not it may access one or more localizedapplications in a given serving cell based on, for example, locationarea and/or coverage area for the concerned application. This may be thecase, for example, in a deployment where an eNB handles localizedapplications in a transparent manner from the perspective of handling ofradio resources of a given cell.

With respect to embodiments where the WTRU receives signaling thatcontains at least some of the above parameters via broadcastinformation, the WTRU may receive parameters related to localizedapplication on a PDSCH transmission scheduled using a DCI received inthe CSS of the PDCCH of the concerned cell and scrambled by an RNTI(e.g., on an SIB scheduled using SI-RNTI or separately using acell-specific RNTI (e.g., LA-RNTI)). In an embodiment, at least someparameters related to localized applications may be received on an MBMStransmission.

For example, a WTRU in idle or connected mode may receive one or moreparameters related to localized information in an SIB on the broadcastsystem information as part of the system information acquisition (incase of mobility when moving to the concerned cell) or as part of itsupdate procedure for system information. The WTRU may detect anindication that localized applications are supported in the concernedcell (e.g., from reception of an SIB such as SIB2) and determine thatlocalized applications are supported in the concerned cell. The WTRU mayinitiate a connection to the network to obtain further parameters forlocalized applications using, for example, dedicated signaling.Alternatively, the WTRU may detect the presence of an SIB specific forlocalized applications and determine that localized applications aresupported in the concerned cell.

In an embodiment, the SIB may include scheduling information (e.g.,LA-RNTI) such that the WTRU may receive further parameters on the PDSCHsuch as a list of available applications and parameters, if any.Alternatively, the SIB may include a list of available services andparameters, if any. In an embodiment, the WTRU may use the receivedinformation to determine whether or not to initiate a registration tothe application.

With respect to embodiments where the WTRU receives signaling thatcontains at least some of the above parameters via dedicated signaling,the WTRU may receive parameters related to localized applications on aPDSCH transmission scheduled using a DCI received in the CSS of thePDCCH of the concerned cell and scrambled by the WTRU's C-RNTI. In anembodiment, at least some parameters related to localized applicationsmay be received using an RRC transaction (e.g., an RRC reconfigurationprocedure) and/or using a higher layer protocol (e.g., transported in anRRC PDU) for transactions between the WTRU and an LAIS. Alternatively,at least some parameters related to localized applications may bereceived using a MAC control element.

A WTRU may include, as part of its WTRU capability, an indication thatit supports access to localized services. The WTRU may then beconfigured by the eNB with the necessary parameters to access theservices, if supported and/or available in the serving cell. Forexample, a WTRU in connected mode may be configured by the network withscheduling information (e.g., LA-RNTI) such that the WTRU may receivefurther parameters on the PDSCH such as a list of available applicationsand parameters, if any. In an embodiment, this may be based on theWTRU's capability as indicated during the initial connection setup. Inan embodiment, the configuration may include a list of available serviceand parameters, if any. In an embodiment, the WTRU may use the receivedinformation to determine whether or not to initiate a registration foran application.

With respect to embodiments where the WTRU receives signaling thatcontains at least some of the above parameters via higher layersignaling, a WTRU in connected mode may receive at least some of theparameters using a higher layer protocol (e.g., transported in an RRCPDU). For example, the WTRU may receive a list of applications and/orservice types available for the WTRU from the LAIS server. In anembodiment, this may be part of a request-response transaction betweenthe WTRU and the LAIS, which transaction may include the exchange ofparameters related to the position and/or location of the WTRU, userprofile and/or security parameters.

When the WTRU has access to parameters related to localizedapplications, the WTRU may additionally initiate a location and/orpositioning-related procedure either when it detects that the cellsupports localized applications or when it determines that it shouldinitiate a registration procedure. In an embodiment, the WTRU mayinitiate such additional procedures autonomously, based on a userprofile stored within the WTRU and/or upon input from a user of theconcerned WTRU (e.g., for pull services). Alternatively, the WTRU mayinitiate such procedures when it receives a request from the network(e.g., either from the eNB or from the LAIS). For example, in suchcases, the WTRU may activate a GPS module, initiate a location updateand/or a traffic area update (e.g., towards the MME), initiate apositioning request/update procedure (e.g., with an LCS using, forexample, an A-GPS procedure, OTDOA, cell-ID based positioning or anyother positioning method), determine position-related parameters thatmay be used for proximity detection, initiate proximity detection for atleast one application of interest.

A WTRU may determine what localized applications are available byperforming a procedure to detect that it is within the location area ofa localized application of interest (e.g., discovery) by, for example,autonomously determining that it is within the location area of a givenapplication (e.g., a pull behavior), transmitting a request to a networknode (e.g., a pull behavior), receiving an indication from the networkthat it is within the location area of a given application (e.g., a pushbehavior), or determining that an MBMS session (e.g., one or more MTCHs)that corresponds to the concerned application is scheduled (e.g., onMCCH) in the concerned cell. With respect to the WTRU autonomouslydetermining that it is within the location area of a given application,the application may be advertised in the cell (e.g., listed in an SIB orother information received on a PDSCH transmission). With respect to theWTRU transmitting a request to a network node, for example, the WTRU maytransmit position information to the LAIS together with a request for alist of applications available in the corresponding area. In anembodiment, the WTRU may do this only for a certain type of application.The WTRU may receive LAI for a list of applications that matches thecriteria indicated in the request.

With respect to the WTRU receiving an indication from the network thatit is within the location area of a given application, the WTRU mayreceive an indication from the network that an application is available.In an embodiment, the indication may be received from the LAIS. In anembodiment, the WTRU may receive the indication for an application towhich the WTRU has previously registered. In an embodiment, theindication is a request for the WTRU to initiate communication with theapplication.

For example, a WTRU may register to the concerned application (e.g.,availability) and/or initiate communication for the concernedapplication (e.g., accessibility) when a criterion is met. For example,an application may be available within a specific geographical area. Asanother example, the criterion may be that the WTRU's position is withina certain area. Examples of areas may include a geographical positionwith a given error margin, a sector of a cell, a cell, reception ofsignals from a given eNB, reception of discovery-related signals from asecond WTRU (for example, above a given threshold in signal strengthand/or according to an identity broadcast in the discovery-relatedsignal), a tracking area, or a cell served by a given MME.

With respect to the WTRU determining that an MBMS session thatcorresponds to the concerned application is scheduled in the concernedcell, a WTRU that determines that a localized application of interest isavailable in a given area may perform an initial access to the network,register to the LAIS, perform more frequent positioning updates orperform a tracking area update (TAU).

A WTRU in idle mode may discover that an application of interest isavailable according to a method described above. The WTRU may thenperform an initial access to the network (e.g., a transition from idlemode to connected mode), for example, to register and/or access theconcerned application or to perform a procedure to determine itsposition. For example, the WTRU may discover an application of interest,determine that it is within the location area of the concernedapplication, register to the application and update its positioninginformation to determine whether or not the criterion regarding thecoverage area of the application is met.

With respect to a WTRU registering to the LAIS, a WTRU registering tothe LAIS may enable the network to manage mobility, positioning,tracking and session initiation for the concerned WTRU and for theconcerned service.

With respect to a WTRU performing more frequent positioning updates, theWTRU may perform a positioning procedure at regular intervals, and/ormaintain a positioning method active while it is within the locationarea of an application of interest. In an embodiment, the WTRU mayperform a positioning procedure at regular intervals and/or maintain apositioning method active while it is within the location area of anapplication for which the WTRU has previously registered to with theLAIS. The update frequency may be a function of distance and speed(e.g., difference between previous position divided by time since lastupdate) to save battery and network load, in particular, if locationarea is not directly overlapping (e.g., equivalent) to the coverage areafor the concerned application.

With respect to a WTRU performing a TAU, for example, a WTRU in idlemode may perform cell re-selection and may camp on a different cell. TheWTRU may determine that the cell supports localized applications and maydetermine that it is interested in a specific application, independentlyof whether or not the WTRU can determine if a concerned application isavailable in the concerned cell. The WTRU may perform the TAU procedure.Subsequently, the WTRU may receive paging. In particular, the networkmay determine, based on the WTRU's location, whether or not the WTRUshould initiate communication to a given application (e.g., a registeredapplication), for example, in case of push services.

Whether or not an application is available and/or is accessible may bedetermined as a function of at least one of the position of the WTRU,the location area of the application (e.g., as indicated by LAI), thecoverage area of the application (e.g., as indicated by LAI), receptionof discovery-related signals from a second WTRU that is a server or peerfor the concerned application (for example, above a given threshold insignal strength and/or according to an identity broadcast in thediscovery-related signal) whether or not the WTRU is registered for theconcerned application, whether or not the WTRU's position meets thecriterion for location area and/or for coverage area for the concernedapplication, the WTRU capabilities, the subscriber information and/orprofile for the WTRU, the user's credentials (e.g., for the LAIS and/orfor the concerned application) and/or group membership. This may bedetermined either by the WTRU (e.g., for pull behavior) or by the LAIS(e.g., for push behavior).

For example, whether or not an application is available for a given WTRUmay be a function of the WTRU's position and the application's locationarea, in which case the WTRU may register to the LAIS for the concernedapplication. For example, whether or not a WTRU may connect to a sessionof an application may be a function of the WTRU's position, the WTRU'sgroup membership/credentials and the application's coverage area for thecorresponding session, in which case the WTRU may establish a connectionto the session of the concerned application. In another example, theprevious examples and related steps may be combined for an applicationfor which the location area and the coverage area directly overlaps,and, in an embodiment, for which proximity detection is detected (e.g.,based on the WTRU's mobility to a cell within the location area of theconcerned application).

A WTRU may detect that it is within the proximity of (or that it hasentered) an area where it may access a localized application. This areamay correspond to the location area of the concerned application or tothe coverage area within the location area of the application, ifspecified. The coverage area may be identical to the location area for agiven application.

For example, a WTRU may determine that an application is available, thatit is within the location area of the application, and register to theapplication. When it determines that it is within the coverage area ofthe concerned application, it may initiate communication with theapplication. Once it leaves the coverage area, it may stop communicationwith the application. In an embodiment, the WTRU may remain registeredto the application. In an embodiment, the WTRU may maintain itsregistration until it leaves the location area of the application.

In an embodiment, the proximity detection may be performed by thenetwork. The IE may receive a network-initiated transmission for theconcerned application when it determines that the WTRU is within thecoverage area of the application (e.g., push behavior). This may bebased on a network-controlled positioning method.

The application service hosting the application may be any one of anumber of different entities including, for example, another WTRU or anetwork entity such as an LAI server (LAIS). An LAIS may be used toenable connectivity between devices (e.g., peers, servers or clients),between network nodes and/or between combinations thereof for a givenlocalized application. The LAIS may be external to the WTRU. The LAISmay be either a stand-alone entity, co-located with another entity orintegrated into another entity. The LAIS may be located in the network(e.g., in the EPS) or in another mobile device. In one example, the LAISmay be co-located with an MME. In another example, the LAIS may beco-located or integrated with a LCS server. In another example, the LAISmay be co-located or integrated with an eNB. In another example, theLAIS may be co-located with an application server or in a peer (e.g., inany device connected to the network).

A WTRU may communicate with the LAIS by, for example, requesting LAI,receiving LAI, transmitting LAI for a given application, registering toan application, de-registering from an application, exchanging a userprofile, network-initiated application setup, or WTRU-initiatedapplication setup.

A WTRU may request LAI for one or more applications and/or applicationtypes from the LAIS. For example, a WTRU may initiate transmission of arequest by determining that the cell supports localized applications,performing a procedure to determine its position and/or communicationwith an LCS or being notified by the network (e.g., being notified ofthe availability of LAIS).

A WTRU may also receive LAI from the LAIS. In an embodiment, a networknode may initiate the transmission of LAI to a WTRU, for example, to aWTRU that has previously registered to the application (or forinformation regarding a type of application). For example, the networknode may determine that the WTRU is within the location and/or coveragearea of the concerned application. In an embodiment, this may befollowing a procedure by the WTRU to determine the WTRU's position. Asanother example, the network node may transmit LAI upon registration bythe WTRU (e.g., to the core network such as an NAS ATTACH procedure). Asanother example, the network may transmit LAI to the WTRU following atraffic area update procedure for the WTRU. As another example, thenetwork node may transmit LAI based on the WTRU's capabilities.

A WTRU may transmit LAI pertaining to an application initiated by theWTRU (e.g., a peer-to-peer application) or to a service offered by theWTRU to the LAIS.

A WTRU may register to an application, for example, as a client, as aserver or as a peer for a given application and/or session. In anembodiment, a registration may have a validity period and may requireperiodic updating.

A WTRU may de-register from an application, for example, as a client, asa server or as a peer for a given application and/or session. Forexample, the WTRU may transmit an explicit request to the LAIS tode-register from an application. Alternatively, the LAIS may indicate tothe WTRU that it is no longer registered for a given application.Alternatively, a registration may expire or may no longer be valid, forexample, following a specific event (e.g., a mobility event such as achange of cell, MME, Tracking Area outside of the location area and/orthe coverage area of the concerned application, or the position criteriafor the application being no longer met).

The WTRU may transmit user-related information such as a profileincluding application identity of interest or application type ofinterest, for example, for push services.

The WTRU may receive a request from the LAIS to establish a session, forexample, with another WTRU, for a given application and/or session. TheWTRU may respond with an acknowledgement for the request, for example,only for an application and/or session for which the WTRU has previouslyregistered with the LAIS. Alternatively, the WTRU may initiate aregistration for the given application in response to the request.

The WTRU may transmit a request to the LAIS to establish a session, forexample, with another WTRU, for a given application and/or session.Here, the WTRU may receive a response from the LAIS that includes LAIfor the specific application and/or session, for example, only for anapplication for which the WTRU has detected proximity and/or only for anapplication and/or session for which the WTRU has previously registeredwith the LAIS.

The WTRU and the LAIS may, for example, communicate using arequest-response type of protocol. Transactions between a WTRU and anLAIS may be transported as higher-layer data within the RRC protocol,where the eNB may forward the transaction to the proper LAS.Alternatively, a WTRU configured with necessary IP parameters tocommunicate with the LAIS may transmit data over a data radio bearer(DRB) in a manner transparent to the RAN.

In an embodiment, the LAIS may store and maintain subscriber profileinformation for a given WTRU. For example, the LAIS may store profileinformation temporarily, for example, while the WTRU is registered to atleast one localized application of the LAIS.

In an embodiment, the LAIS may initiate a connection to a mobile deviceregistered (e.g., interested) to a localized application (e.g., aservice or a peering application), for example, for push applicationsand if the LAIS determines that the positioning information applicableto the WTRU matches the location area and/or coverage area of theconcerned application.

To communicate with the LAIS, the WTRU may be provided with thenecessary communication parameters (e.g., IP address), for example, ifcommunication between the LAIS and the WTRU is transparent to the eNB.For example, the WTRU may receive such parameters in an NAS messagewhen, for example, it performs the ATTACH procedure, or in an RRCmessage when the WTRU is configured. Alternatively, the eNB may directthe transactions between the WTRU and the LAIS to the LAIS configuredfor the corresponding eNB, for example, if RRC is used as the transportprotocol.

To communicate with a given application session, the WTRU may receiveLAI including communication parameters for the concerned session. TheWTRU may receive the LAI, for example, upon request for LAI to the LAIS,upon registration to the LAIS or upon an application setup eitherrequested by the WTRU or by the network.

A WTRU in connected mode may register that it is interested in receivingand/or transmitting information for a localized application byregistering to the LAIS, registering to a localized application and/orsession, registering as a server, registering as a client, orregistering as a peer.

For a WTRU registering to the LAIS, for example, the WTRU may perform atransaction with the LAIS such that the WTRU registers to the LAIS. Sucha transaction may include, for example, establishment of security andaccess credentials between the WTRU and the LAIS as well as exchange ofthe list of localized applications available to the WTRU and associatedparameters, if any. Once registration is confirmed, the WTRU may performfurther registrations and/or monitor cell broadcast for applicationsavailable in the concerned cell.

For a WTRU registering to a localized application and/or session, forexample, the WTRU may perform a transaction with the LAIS such that theWTRU registers to a localized application/session of interest. The WTRUmay then perform proximity detection or detection of discovery-relatedsignals from a second WTRU. Alternatively, the WTRU may register to anongoing session for a given application. Once registration is confirmed,the WTRU may then immediately join the session and initiate receptionand/or transmission for the application. Such transaction may includeestablishment of security and access credentials between the WTRU andthe LAIS for the concerned application and/or session.

For a WTRU registering as a server, for example, the WTRU may perform atransaction with the LAIS such that the WTRU registers itself as aserver for a localized application. Such transaction may include, forexample, establishment of security and access credentials between theWTRU and the LAIS for the concerned application as well as exchange ofcommunication parameters for the concerned service. Once registration isconfirmed, the WTRU may then wait for reception of incoming requestsfrom other clients.

For a WTRU registering as a client, for example, the WTRU may perform atransaction with the LAIS such that the WTRU registers itself as aclient for a localized application. Such transaction may includeestablishment of security and access credentials between the WTRU andthe LAIS for the concerned application as well as exchange ofcommunication parameters for the concerned service. Once registration isconfirmed, the WTRU may then initiate requests to the server of theapplication.

For a WTRU registering as a peer, for example, the WTRU may perform atransaction with the LAIS such that the WTRU registers itself as a peerfor a localized application. Such transaction may include establishmentof security and access credentials between the WTRU and the LAIS for theconcerned application and/or session as well as exchange ofcommunication parameters for the concerned service. Once registration isconfirmed, the WTRU may then initiate transmission/reception ofapplication traffic.

Each of the transactions described above may include exchange of userprofile information and exchange of positioning information. Userprofile information may further include session specific informationand/or access credentials (e.g., a session identity, a group identity,or application subscription information).

In an embodiment, the WTRU may unregister any of the above registrationswhen the registration is no longer needed. In an embodiment, any of theabove registrations may expire (e.g., time out), for example, when theWTRU may no longer communicate with the LAIS or when the WTRU does notupdate the concerned registration.

The network may establish communication between a plurality of WTRUs anda localized application such that the RAN may forward application datawithin the same eNB (e.g., if all concerned WTRUs are connected to cellsof the same eNB) or from one eNB to another, for example, over X2otherwise.

In an embodiment, a WTRU may be configured by the eNB with specificradio resources for a given application such that WTRUs may communicate,for example, directly with each other. Alternatively, the WTRU mayreceive control signaling for dynamic or semi-static scheduling ofresources for a given application.

The WTRU may differentiate data for a localized application using atleast one of the following. The WTRU may be configured to use a specificIP destination address (and, in an embodiment, a specific port number)for the given application (e.g., a multicast address and/or the IPaddress of a MBMS server with a port number for the concernedapplication/session). In an embodiment, whether or not the MBMS serveris used may be a function of the number of WTRUs registered to theconcerned application. The WTRU may be configured with a specificlogical channel (LCH) and/or DRB identity for the given application. TheWTRU may be configured with a specific logical channel group (LCG) forthe given application.

This may permit differentiation of data between localized applicationsand other types of applications. In an embodiment, data for localizedapplications may be transmitted using radio resources specificallyindicated for localized applications (e.g., by L1 signaling such asusing a specific DCI, a specific RNTI, or a flag indication in the DCIformat). In an embodiment, DL data may be received by multiple WTRUsusing the same RNTI, for example, an application-specific and/orcell-specific RNTI. The WTRU may be configured to receive DL data forthe concerned application on a MBMS channel.

In addition to managing LAI, the LAIS may also manage registrationstatus to a given localized application, such as service registrationstate, client registration, peering registration and applicationtriggers. With respect to service registration state, for example, theLAIS may manage a list of services, which may be registered by WTRUs. Inan embodiment, the list of services may be a list of WTRUs that arecommunicating with the registered server, applicable group membershipand credentials. With respect to client registration (e.g., interest fora given service), the LAIS may manage a list of WTRUs that haveregistered for the service, such as a list of WTRUs that arecommunicating with the registered server, applicable group membershipand credentials. With respect to peering registration, the LAIS maymanage a list of WTRUs that have registered for the application, such asa list of WTRUs that are communicating with the application, applicablegroup membership and credentials. With respect to application triggers,the LAIS may manage a list of criteria for each application, by whichthe LAIS may initiate a procedure for a WTRU to communicate with theapplication (e.g., push behavior), for example, based on groupmembership and/or a user's profile.

In an embodiment, the LAIS may interact with other network nodes (e.g.,with an eNB, an MME, an LCS and/or an MBMS server). In an embodiment,any of the above information may be exchanged between concerned nodes.Additional interactions may also be possible between the LAIS and othernetwork nodes (e.g., with an eNB, an MME, an LCS and/or an MBMS server).

With respect to interactions between the LAIS and an MME to trigger apush application, the LAIS may receive an indication that a WTRU has anew position and/or the position (or updates thereto) of the WTRU froman MME, either from an update procedure (e.g., following a TAU or due toconnected mode mobility) between the MME and the WTRU or from a requestfrom the LAIS to the MME. In an embodiment, the LAIS may receivesubscriber profile information from the MME application to the concernedWTRU. In an embodiment, the LAIS may indicate to the MME that a givenWTRU may be paged, either to initiate communication, for performing aTAU procedure and/or to determine a WTRU's location. For example, theLAIS may perform such actions for push services based on a WTRU'sposition.

With respect to interactions between an LAIS and an LCS to trigger apush application, the LAIS may, for example, receive an indication thata WTRU has a new position and/or the position (or updates thereto) of aWTRU from an LCS, either from an update procedure (e.g., following apositioning procedure) between the WTRU and the LCS or from a requestfrom the LAIS for the concerned WTRU.

With respect to interactions between an LAIS and an MBMS server toexchange information and/or register an MBMS service, the LAIS mayregister an MBMS service to the MBMS server for a localized application.The LAIS may receive information necessary to access an MBMS servicecorresponding to a localized application (e.g., what MBSFN area (e.g.,the MBMS cell group identity) and/or what MBMS control channel (MCCH)may be used to access the DL broadcast for a given application). Thismay also include an identity of the MBMS service that corresponds to theconcerned application.

With respect to interactions between an LAIS and an eNB to provideinformation for cell broadcast, for example, the LAIS may provideinformation that an eNB may transmit to one (e.g., using dedicatedsignaling) or more WTRUs (e.g., using system information broadcastand/or a common channel for localized application) based on at least oneof availability of one or more localized applications (e.g., whether ornot a cell supports localized applications) or information related tolocalized applications. Information about availability of one or morelocalized applications, for example, may be used by a WTRU to determinewhether or not a cell supports localized services. Information relatedto localized applications may include, for example, a list of one ormore localized applications available for the concerned cell, if any,or, for a given application, additional information related to alocalized application. For example, this information may be used by aWTRU for registration, for discovery and/or for proximity detection of alocalized application.

Examples of localized applications may include client-serverapplications, peer-to-peer applications, direct WTRU to WTRUcommunications (with or without assistance from the cellularinfrastructure to manage the allocation of radio resources) and Wifioffload applications.

With respect to client-server applications, for example, anun-registered server may first determine that localized services areavailable in an area and may then register the service. The network maystart advertising the service on behalf of the server such that a clientmay determine that at least one service of interest is available in thearea. The WTRU may then start a procedure to wait for or detect aproximity indication (it may be the same as a discovery procedure withina cell or based on reception of discovery-related signals from a secondWTRU, or something based on positioning within a cell depending on thegranularity). Once at proximity, the client may access the localizedservice.

Different types of client-server applications may include, for example,pull services and push services. An example of a pull service mayinclude a marketing application. For example, a user may enter a store,request a list of product types according to some criteria, requestfurther information and then locate and pay for the products. Anotherexample of a pull service may include a personal youtube event. Forexample, a user may enter a location for an event, request a list ofavailable streams related to the event and select a specific stream(e.g., buy or download an album at a discount). An example of a pushservice may include a marketing application. For example, a user mayenter a store, receive targeted offers based on profile, interest,shopping list and/or actual position and locate and pay for the offeredproduct/service. Another example of a push service may include apersonal youtube event. For example, a user may enter a location and anevent, receive streaming from members of the group and/or group chat, orgroup voice sessions.

With respect to peer-to-peer applications, for example, an un-registeredpeering application may first determine whether localized services areavailable in an area and may then register the availability/interest ofthe device to the LAIS for at least one peer-to-peer application. TheWTRU may then start a procedure to wait for or detect a proximityindication (it may be the same as a discovery procedure within a cell orbased on reception of discovery-related signals from a second WTRU, orsomething based on positioning within a cell depending on thegranularity).

Different types of peer-to-peer applications may include, for example,pull services and push services. For a pull service, the user mayinitiate the registration to the LAIS. For a push service, the LAIS mayinitiate the setup of the peering application based on a stored userprofile and interest.

For either of client-server or peer-to-peer applications, the setup maybe that once connected to the network, the WTRU may receive user planedata for the localized application using network-allocated dedicatedresources for both UL and DL transfers (applicable to both directdevice-to-device communications or through the radio access network).Alternatively, the WTRU may be configured for MBMS reception for the DLuser plane for the localized application.

With respect to direct communication between two or more WTRUs (with orwithout assistance from the cellular infrastructure to manage theallocation of radio resources), a wireless system may use the localizedapplication principles and framework described above to realizemanagement of connectivity for the purpose of offloading user data fromthe cellular network.

With respect to Wifi offload applications, a cellular system may use thelocalized application principles and framework described above torealize management of connectivity for the purpose of offloading userdata from the cellular network. Such embodiments may be equallyapplicable to the Home eNB, Home NB and other types of small cell andpico-cell deployments.

FIG. 5 is a flow diagram of an example method of Wifi offload usinglocalized applications. A WTRU (e.g., a WLAN AP) may determine thatlocalized services are available in a location (502) and register to aWifi offload service (e.g., an LAIS) (504). In an embodiment, the WTRUmay register itself to the Wifi offload service using a fixed IPinterface and may also implement a cellular technology and register tothe Wifi offload service using an established RRC connection. Atransport channel may be established between the WTRU and the cellularnetwork for data offload (506). In an embodiment, the Wifi offloadservice (e.g., the LAIS) may initiate a connection to the WTRU toestablish the connection. The WTRU may receive control signaling (508).The WTRU may receive the control signaling from the cellular network foran offload operation. In an embodiment, the cellular network may triggerWifi offload for a given WTRU based on a detection that the SLAN WTRU iswithin proximity of a Wifi offload service provided by a WLAN AN.

For example, a WLAN AP may support methods to provide Wifi offloadservices. The WLAN AP may first determine that localized services areavailable in an area. The WLAN AP may then register itself to the Wifioffload service (if available). For example, the WLAN AP may register tothe LAIS using a fixed IP network interface. The WLAN AP mayadditionally implement a cellular technology (e.g., HSPA or LTE) andregister to the LAIS using the corresponding wireless IP networkinterface. For example, if the network implements LAIS in the RAN (e.g.,in or above the RRC layer), the WLAN AP may simply issue an RRC requestto register itself to the LAIS using an established RRC connection. Asanother example, if the network implements LAIS in the core network(e.g., in or above NAS), the WLAN AP may simply issue an NAS request toregister itself to the LAIS using an established RRC connection.

In this case, in an embodiment, the WLAN AP may use 3GPP-basedsubscription credentials when it registers itself for the Wifi offloadservice to the network for security and/or authentication purposes. Theregistration for the offload service may include parameters including atleast one of WLAN AN identity-related information (e.g. parametersrequired for 802.11 WLAN AN identification), security-relatedinformation (e.g. parameters required for 802.11 authentication),access-related information (e.g. parameters required for 802.11association), discovery-related information (e.g. parameters requiredfor 802.11u functionality), selection-related information (e.g.parameters required for 802.11u functionality), location-relatedinformation (e.g. parameters required for localized applicationfunctionality), and type and parameters of the offload service (e.g.parameter required to the functionality of the cellular system).

WLAN AN identity-related information may include at least one of anidentity of the Wifi network (e.g., Basic SSID and/or a MAC identity),access credentials (e.g., subscriber-based parameters) or operatingchannel/frequency. As another example, in case of offload to a Home eNBor similar, instead of offloading to a Wifi network, this may be based aclosed subscriber group (CSG) identification (CGI), a physical cellidentification (PCI) and/or a CSG list.

Security-related information may include at least one of the type ofsecurity protocol, the type of encryption algorithm, or the securitykey. The type of security protocol may be, for example, one of a wiredequivalent privacy (WPA), Wifi Protected Access (WPA) or WPA II (WPA2).The type of encryption algorithm may be, for example, one of a temporalkey integrity protocol (TKIP), or a pre-share key mode (PSK). Thesecurity key may be, for example, a string of hexadecimal digits, or abitstring. In an embodiment, it may correspond to information (e.g., apassphrase) from which a Wifi device further derives the encryption keyusing a known key derivation function.

Access-related information may include supported access data rates orother similar information. Discovery related information may include atleast one of access network type, roaming information and venueinformation. Selection-related information may include at least one ofdomain name, credential type or EAP methods.

Location-related information may include at least one of a location areafor the offload service and coverage area for the offload service. Thelocation area for the offload service may correspond to the location ofa plurality of WLAN APs that belong to the same WLAN AN and that mayprovide continuous pedestrian coverage. The coverage area for theoffload service may correspond to the coverage area of a plurality ofWLAN APs that belong to the same WLAN AN and that may provide continuouspedestrian coverage.

Type and parameters of the offload service may include at least one ofwhether the WLAN AN (or WLAN AP) supports cellular-assisted withredirection offload, cellular-controlled offload service or both andparameters for the offload service in case of cellular-controlledoffload service. For example, this may include connectivity informationfor the cellular system (e.g., either the RAN or the CN) necessary toestablish an interface for the transfer of user data over the wiredinterface of the WLAN AP (e.g., from a RAN perspective, similar to an X2interface or from a CN perspective, similar to an IP tunnel).

A WLAN AP may register itself to the LAIS as a server that can provideWifi offload services. For example, on a condition that the WLAN APsupports an offload service, the WLAN AP may register to the LAIS withWLAN AN identity-related information (e.g., SSID), security-relatedinformation for Wifi shared authentication, or access-relatedinformation (e.g., supported data rates). The registration may alsoinclude, in an embodiment, discovery-related information and/orselection-related information, for example, if WLAN APs belonging to adifferent network operator than the cellular operator are allowed toregister to the LAIS as offload servers. Otherwise, this information maybe based on other credentials of the WLAN AP, such as USIM-relatedcredentials, and/or if roaming between offload servers belonging todifferent network operators is possible.

The LAIS may then store the information received during the registrationprocess. For a WLAN AN (or WLAN AP) supporting a cellular-controlledoffload service, the LAIS may initiate a connection to the WLAN AN (orWLAN AP) to establish a transport channel between the cellular systemand the WLAN AN/AP. In an embodiment, this connection may be establishedonly when a first WLAN WTRU is configured (either via an inter-RAThandover to the Wifi offload network or via a reconfiguration thatindicates the WLAN AN offload) for offload operation.

A WLAN WTRU may register itself to the LAIS as a client interested inWifi offload services. For example, for a WTRU that supports Wifi andalso supports an offload service, the WLAN WTRU may register to theLAIS. In an embodiment, the WLAN WTRU may include capability-relatedparameters in the registration (e.g., supported data rates, supportedsecurity protocols and encryption methods) and other capabilitiesrelated to Wifi operation necessary to access a WLAN AN.

The WLAN WTRU may also provide location information (e.g., upon requestfrom the cellular system) according to any of the methods describedherein. For example, the network may trigger the Wifi offload for agiven WTRU based on detection that the WLAN WTRU is within proximityand/or within the coverage area of a Wifi offload service provided by aWLAN AN. In an embodiment, this may additionally be triggered incombination with indications of congestion in the cellular system and/orinsufficient resources in the cellular system to serve data traffic forthe given WTRU.

The WLAN WTRU may subsequently receive control signaling from thecellular network (either via an inter-RAT handover to the Wifi offloadnetwork or via a reconfiguration that indicates the WLAN AN offload) foroffload operation. As part of the signaling, the WTRU may be providedwith a list of information to assist it in configuring the clientaccordingly or in finding the offload AP and to assist in determiningthe correct AP to connect to. Such information may include one or acombination of the information exchanged during registration (asdescribed above) for the offload service for the WLAN AP. Suchinformation may include, for example, WLAN AN identity-relatedinformation, security-related information, discovery-relatedinformation, and location-related information. This may also beapplicable to initiating an offload to a WLAN AP, wherein the networkindicates to the WTRU the information required to search and connect toa WLAN AP. The WLAN WTRU may activate a Wifi module following thereception of control signaling from the cellular system that initiatesthe Wifi offload service.

In another example embodiment, a cellular system may use the localizedapplication principles and framework described herein to realizemobility management for the purpose of handling WLAN WTRU mobilityacross a, for example, heterogeneous deployment of smaller cells thatmay be used to offload user data from the cellular network. Thisembodiment may also be applicable to Home eNB, Home NBs and other typesof small cell and pico-cell deployments.

In an embodiment, a WTRU may send feedback related to the signalstrength of a current WLAN AN, especially if related to disconnecting. Atrigger may stop the Wifi offload service. The trigger may trigger, forexample, some form of reselection for another offload server by acellular network. The WTRU may send feedback related to signal strengthof a visible WLAN AP (passive scanning).

Although features and elements are described above in particularcombinations, one of ordinary skill in the art will appreciate that eachfeature or element can be used alone or in any combination with theother features and elements. In addition, the methods described hereinmay be implemented in a computer program, software, or firmwareincorporated in a computer-readable medium for execution by a computeror processor. Examples of computer-readable media include electronicsignals (transmitted over wired or wireless connections) andcomputer-readable storage media. Examples of computer-readable storagemedia include, but are not limited to, a read only memory (ROM), arandom access memory (RAM), a register, cache memory, semiconductormemory devices, magnetic media such as internal hard disks and removabledisks, magneto-optical media, and optical media such as CD-ROM disks,and digital versatile disks (DVDs). A processor in association withsoftware may be used to implement a radio frequency transceiver for usein a WTRU, UE, terminal, base station, RNC, or any host computer.

1. A method of wireless communication comprising: a wirelesstransmit/receive unit (WTRU) determining a location of the WTRU; theWTRU determining whether an application is available to the WTRU basedon the determined location of the WTRU; and on a condition that theapplication is determined to be available to the WTRU based on thedetermined location of the WTRU, the WTRU initiating access to anapplication service hosting the application.
 2. The method of claim 1,wherein the WTRU determines the location of the WTRU based on at leastone of global positioning system (GPS) positioning, assisted GPS (A-GPS)positioning, observed time difference of arrival (OTDOA) positioning,determining whether the WTRU is located in a sector of a given cell,determining whether the WTRU is located in a given cell associated witha given cell identity, determining whether the WTRU is located within agiven cell area, determining whether the WTRU is located within a giventracking area, a system information element broadcast in a call, amultimedia broadcast multimedia services (MBMS) session available in agiven cell, a Wifi parameter, determining whether the WTRU is located ina mobility management entity (MME) area of a given cell, or determiningwhether the WTRU receives discovery-related signals from another WTRU.3. The method of claim 1, wherein the WTRU initiates access to theapplication service by initiating a registration to the applicationservice using at least one of a network access server (NAS) servicerequest or an NAS ATTACH procedure.
 4. The method of claim 1, whereinthe application service is provided by one of an application server andanother WTRU.
 5. The method of claim 4, wherein the application serviceis provided by the other WTRU via peer-to-peer communications, and theother WTRU provides a data offload service.
 6. The method of claim 4,wherein the application service is provided by the other WTRU viapeer-to-peer communications, and the other WTRU is a Wifi access point.7. The method of claim 1, wherein the WTRU determines whether anapplication is available to the WTRU based on the determined location ofthe WTRU by: receiving localized application information (LAI) relatingto at least one application from the application service; anddetermining whether the at least one application is available to theWTRU based on the received LAI.
 8. The method of claim 7, wherein theLAI includes information about at least a location area of the at leastone application.
 9. The method of claim 1, further comprising: the WTRUperiodically determining whether an application continues to beavailable to the WTRU based on the determined location of the WTRU; andon a condition that the WTRU determines that the application is nolonger available to the WTRU, discontinuing communications with theapplication service.
 10. The method of claim 9, wherein thediscontinuing communications with the application server includesinitiating de-registration from the application service.
 11. A method ofwireless communication comprising: a wireless transmit/receive unit(WTRU) receiving an indication from an application service that a WTRUis within a location area of a given application hosted by theapplication service; and in response to receiving the indication fromthe application service, the WTRU initiating access to the applicationservice hosting the given application.
 12. The method of claim 11,wherein the WTRU initiates access to the application server byinitiating a registration to the application server using at least oneof a network access server (NAS) request or an NAS ATTACH procedure. 13.The method of claim 11, wherein the application service is provided byan application server.
 14. The method of claim 11, further comprisingthe WTRU registering to the given application in order to receive theindication from the application service that the WTRU is within thelocation area of the given application on a condition that the WTRUenters the location area of the given application.
 15. A wirelesstransmit/receive unit comprising: a processor configured to: determine alocation of the WTRU, determine whether an application is available tothe WTRU based on the determined location of the WTRU, and on acondition that the application is determined to be available to the WTRUbased on the determined location of the WTRU, initiate access to anapplication service hosting the application.
 16. The WTRU of claim 15,wherein the processor is configured to determine the location of theWTRU based on at least one of global positioning system (GPS)positioning, assisted GPS (A-GPS) positioning, observed time differenceof arrival (OTDOA) positioning, determining whether the WTRU is locatedin a sector of a given cell, determining whether the WTRU is located ina given cell associated with a given cell identity, determining whetherthe WTRU is located within a given cell area, determining whether theWTRU is located within a given tracking area, a system informationelement broadcast in a call, a multimedia broadcast multimedia services(MBMS) session available in a given cell, a Wifi parameter, determiningwhether the WTRU is located in a mobility management entity (MME) areaof a given cell, or determining whether the WTRU receivesdiscovery-related signals from another WTRU.
 17. The WTRU of claim 15,wherein the processor is configured to initiate access to theapplication server by initiating a registration to the applicationserver using at least one of a network access server (NAS) servicerequest or an NAS ATTACH procedure.
 18. The WTRU of claim 17, whereinthe application service is provided by the other WTRU via peer-to-peercommunications, and the other WTRU is a Wifi access point.
 19. The WTRUof claim 18, wherein the application service is provided by the otherWTRU via peer-to-peer communications, and the other WTRU provides a dataoffload service.
 20. The WTRU of claim 15, wherein the applicationservice is provided by one of an application server and another WTRU.